Relationship Between Data Services and Models
This page last changed on Feb 26, 2008.
Oracle Data Service Integrator Documentation > Data Services Developer's Guide Relationship ModellingIn large enterprises modeling is — or at least should be — an early task in developing a data services layer. By starting with a graphical representation of data resources it is easier to view data resources globally, leveraging existing information in interesting and useful ways. It is also easy to see opportunities for creating additional business logic in the form of logical services. Model diagrams are quite flexible; they can be based on existing data services (and corresponding underlying data sources), planned data services, or a combination. You can also create and modify data services and data service XML types directly from the model. Relationships can be surfaced through the Relationship Modeler in several ways:
Relationship functions allows data associated with one data service (such as Customer) to serve as a complex parameter for a related data service (such as Orders). Models can represent any combination of logical and physical data services.
Many data service-related operations can be performed from the relationship modeler including:
Navigation functions are visible as properties of each data service in the binary relationship. They can be fully inspected in the Source editor for each data service. Navigation functions also appear as mouse-over text over each endpoint of the relationship line. By default, types shown in model diagrams are XML schema types, but you can change this to display native data source types in the case of physical data services.
|
![]() |
Document generated by Confluence on Jan 13, 2009 15:57 |